Some questions atm

1. Does the JLink runner always load the binary again, or does it simply used what was previously flashed to the device? If the latter case, then it's much easier both for west and twister
2. Does the JLink runner run JLinkRTTClient in the foreground or background? I assumed it was in the foreground based on the existence of run_telnet_client() in jlink.py
3. Does the JLink runner run the gdb server in the foreground or background? Based on jlink.py, I believe that the gdb server should be run in the background (which would mean changes to openocd.py)

I'll have to double-check on a different machine and modify as necessary for consistence.

Still need to look at simplifying the Twister integration, but it should really be something along the lines of

twister \
  -i \
  -p <board> \
  --device-testing \
  --west-flash \
  --west-runner $RUNNER \
  --device-serial-pty rtt \
  -T samples/hello_world

Kind of awkward, but the --device-serial-pty script part might need .elf awareness for openocd, unless we want to use the base of SRAM and the size of SRAM as the search parameters for rtt setup. Otherwise, it would be kind of nice to specify something like --device-serial-pty rtt and to let twister sort out the app-specific details.

In any case, the openocd setup seems to be much more reliable than the JLink setup, although it's possible that the main problem with the JLink setup was due to #81194.

Just to follow up here

1. Does the JLink runner always load the binary again, or does it simply used what was previously flashed to the device? If the latter case, then it's much easier both for west and twister

JLink does not load the binary via the rtt runner, and so that functionality was removed for openocd runner as well to be consistent.

2. Does the JLink runner run JLinkRTTClient in the foreground or background? I assumed it was in the foreground based on the existence of run_telnet_client() in jlink.py

It is run in the foreground.

3. Does the JLink runner run the gdb server in the foreground or background? Based on jlink.py, I believe that the gdb server should be run in the background (which would mean changes to openocd.py)

It is run in the background (or rather, the TCP port is left open for gdb clients to connect).

The two runners should behave quite similarly now.

• fixed comments
• split fix for R0201 into separate commit
• rebased on latest from main

• reworded git commit messages to be be more uniform

@topisani PTAL

reassigning, does not really fall under build system, or any other area that I can tell

Looks like unrelated tests are failing - rebased (hopefully the unrelated issues are fixed already)

@pdgendt - please revisit when you have a moment

Sorry for the wait, LGTM